External device interface abstraction

ABSTRACT

Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for executing a user interface on a computing device, generating one or more event handlers executed on the computing device, each event handler corresponding to a local device service file, receiving first data at a first event handler of a first local device service associated with a first device that is in electronic communication with the computing device, generating, using the first event handler, a first event that includes the first data, receiving, at an external device service, the first event, generating, using the external device service, a first external device event based on the first event, and performing a first action based on the external device event.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of and claims priority toU.S. application Ser. No. 14/275,621, filed on May 12, 2014, which is acontinuation application of and claims priority to U.S. application Ser.No. 13/330,163, filed on Dec. 19, 2011, now U.S. Pat. No. 8,763,016.

BACKGROUND

In some industries, such as the travel service industry, computerapplications can be required to communicate with various devices. Usingthe travel service industry as an example, a passenger check-inapplication can be required to communicate with scanners, scales and/orprinters to facilitate check-in of passengers and printing of documents.In some cases, the addition and/or removal of devices can requiremodification of the application to account for a new device and/orremoval of a device.

SUMMARY

Implementations of the present disclosure include computer-implementedmethods that can be performed using one or more processors and thatinclude the actions of executing a user interface on a computing device,generating one or more event handlers executed on the computing device,each event handler corresponding to a local device service file,receiving first data at a first event handler of a first local deviceservice associated with a first device that is in electroniccommunication with the computing device, generating, using the firstevent handler, a first event that includes the first data, receiving, atan external device service, the first event, generating, using theexternal device service, a first external device event based on thefirst event, and performing a first action based on the external deviceevent.

In some implementations, actions further include receiving a secondlocal device service, storing the second local device service, receivingsecond data at a second event handler of the second local device serviceassociated with a second device that is in electronic communication withthe computing device, generating, using the second event handler, asecond event that includes the second data, receiving, at the externaldevice service, the second event, generating, using the external deviceservice, a second external device event based on the second event, andperforming a second action based on the second external device event.

In some implementations, the first event handler subscribes to eventsgenerated by at least the first device.

In some implementations, a communication service enables communicationof the first data from the first device to the first local deviceservice. In some implementations, the communication service is exclusiveto the first device and to the first local device service.

In some implementations, the first event further includes a deviceidentifier of the first device and a type of the first data.

In some implementations, actions further include transitioning the firstlocal device service to a “waiting for data” state after transmittingthe first event from the first local device service to the externaldevice service.

In some implementations, the first external device event includes adevice identifier of the first device, a type of the first data and thefirst data.

In some implementations, actions further include transitioning the firstlocal device service to a “waiting for data” state after transmittingthe first event from the first local device service to the externaldevice service.

In some implementations, an application that is executed on thecomputing device and that is associated with the user interface performsthe first action.

In some implementations, the user interface is associated with a userinterface configuration that defines one or more local device servicefiles that are to be used.

In some implementations, the external device service is a local externaldevice service that is executed on the computing device.

In some implementations, the external device service is a serverexternal device service that is executed on a server, the server beingin communication with the computing device.

In some implementations, each of the local device service files isprovided as a dynamic link library (DLL) file.

In some implementations, the first device includes one of a scanner anda scale.

In some implementations, the computing device includes one of a kioskand a terminal.

In some implementations, the first action includes one of checking in apassenger for travel on a travel conveyance and boarding a passenger fortravel on a travel conveyance.

Implementations of the present disclosure include computer-implementedmethods that can be performed using one or more processors and thatinclude the actions of receiving, at a server computing device, a firstexternal device request, the first external device request beinggenerated by an application executing on a client computing device thatis in communication with the server computing device, processing thefirst external device request to generate a server request by modifyingthe first external device request from a first format to a second formatusing a first formatter service, transmitting the server request to adevice, the device performing a first action based on the serverrequest, receiving a communication result from the device, processingthe communication result to generate a server response, and transmittingthe server response to the client computing device.

In some implementations, processing the first external device requestincludes identifying the device from a plurality of devices.

In some implementations, actions further include retrieving formatterrouting data from a data service, the formatter routing data identifyingthe first formatter service as a formatter service that is to be usedbased on a type of the first external device request and the device.

In some implementations, the communication request is generated usingthe formatter service.

In some implementations, the formatter service comprises a dynamic-linklibrary (DLL) that is associated with at least one of the device and atype of the first external device request.

In some implementations, the communication request includes a list ofdata streams that are sent to the device.

In some implementations, the first formatter service calls a dataservice to retrieve formatting data to format data provided in thecommunication request.

In some implementations, actions further include: retrieving servercommunication routing data from a data service, and identifying, basedon the server communication routing data, a server communicationservice, the server computing device communicating with the device usingthe server communication service.

In some implementations, the server communication service is specific toa type of the device.

In some implementations, the server request is transmitted to the deviceusing an external device service that is executed on the clientcomputing device, the device being directly connected to the computingdevice.

In some implementations, the external device service receives the serverrequest and identifies a local device service based on the serverrequest, the local device service communicating the server request tothe device.

In some implementations, a local device service of the external deviceservice retrieves communication routing data from a data service andidentifies a communication service based on the communication routingdata, the local device service communicating the server request to thedevice using the communication service.

In some implementations, the communication service is specific to a typeof the device.

In some implementations, the device comprises a printer and theformatter service is associated with the type of the printer, and theserver request comprises a print request.

In some implementations, the print request includes at least one of aprint boarding pass request, a print baggage tag request, a printreceipt request and a print itinerary request for travel on a travelconveyance.

The present disclosure also provides a computer-readable storage mediumcoupled to one or more processors and having instructions stored thereonwhich, when executed by the one or more processors, cause the one ormore processors to perform operations in accordance with implementationsof the methods provided herein.

The present disclosure further provides a system for implementing themethods provided herein. The system includes one or more processors, anda computer-readable storage medium coupled to the one or more processorshaving instructions stored thereon which, when executed by the one ormore processors, cause the one or more processors to perform operationsin accordance with implementations of the methods provided herein.

It is appreciated that methods in accordance with the present disclosurecan include any combination of the aspects and features describedherein. That is, methods in accordance with the present disclosure arenot limited to the combinations of aspects and features specificallydescribed herein, but also include any combination of the aspects andfeatures provided.

The details of one or more implementations of the present disclosure areset forth in the accompanying drawings and the description below. Otherfeatures and advantages of the present disclosure will be apparent fromthe description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram depicting a system that is operable to executeimplementations of the present disclosure.

FIG. 2 is a detailed block diagram of components of the system of FIG.1.

FIG. 3 is a flowchart illustrating an example process that can beexecuted in implementations of the present disclosure.

FIG. 4 is a flowchart illustrating an example process that can beexecuted in implementations of the present disclosure.

FIG. 5 is a flowchart illustrating an example process that can beexecuted in implementations of the present disclosure.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

Implementations of the present disclosure are generally directed toenabling communication between computer programs and devices interactingwith the computer programs. In some examples, a computer program issuesone or more commands to a device. In some examples, a device activelyprovides data to the computer program (e.g., without prompting by thecomputer program). In accordance with implementations of the presentdisclosure, new devices can be added to the system and communicationbetween applications and the devices can be quickly enabled with minimaleffort.

Implementations of the present disclosure are described herein withreference to an example context that includes the travel industry,airline travel in particular. A non-limiting example used throughout thepresent disclosure includes passenger check-in for travel on a travelconveyance (e.g., an aircraft). It is appreciated, however, thatimplementations of the present disclosure are operable in othercontexts.

FIG. 1 is a block diagram depicting a system 100 that is operable toexecute implementations of the present disclosure. The system 100includes one or more client devices 102, 104, one or more server devices108 and a network 110. The client devices 102, 104 and the serverdevices 108 are able to communicate with one another over the network110. The client devices 102, 104 can each be any type of appropriatecomputing device. In the depicted example, the client device 102 isprovided as a terminal computing device and the client device 104 isdepicted as a kiosk computing device, as discussed in further detailbelow. Each server device 108 includes a processing device 112 and adata store 114. The processing device 112 executes computer instructions(e.g., program code) stored in the data store 114 to perform functions.In some implementations, the network 110 can be a large computernetwork, such as a local area network (LAN), wide area network (WAN),the Internet, a cellular network, or a combination thereof connectingany number of client devices and/or server devices. In someimplementations, each client (e.g., client devices 102, 104) cancommunicate with one or more servers (e.g., server devices 108) via avirtual private network (VPN), Secure Shell (SSH) tunnel, or othersecure network connection. In some implementations, the network 110 caninclude the Internet, a wireless service network and may include thePublic Switched Telephone Network (PSTN). In other implementations, thenetwork 110 may include a corporate network (e.g., an intranet) and oneor more wireless access points.

As noted above, implementations of the present disclosure are discussedin the non-limiting, example context of the travel industry, and anon-limiting example includes passenger check-in for travel on a travelconveyance. In this example context, the client devices 102, 104 can bedevices used for passenger check-in and/or boarding to a travelconveyance (e.g., an aircraft). For example, the client device 102 canbe operated by an agent 120 that checks in passengers and/or boardspassengers to a travel conveyance. To that end, the client device 102can communicate with one or more other devices that are directlyconnected to the client device 102. Example devices can include ascanner 122 (e.g., a barcode scanner, a QR code scanner), a scale 124(e.g., to weigh luggage), a printer 126 (e.g., to print boarding passesand/or receipts) and a reader 128 (e.g., credit card, driver licenseand/or passport reader). In some examples, the scanner 122 can be acomponent of a device such as a boarding gate reader device. Asdiscussed in detail below, the client device 102 can communicate withother devices that can be indirectly connected to the client device 102.For example, the client device 102 can communicate with a networkedprinter.

In another example, the client device 104 can include a passengercheck-in kiosk and can be operated by an agent (e.g., the agent 120)and/or by a passenger 130. For example, the passenger 130 can use theclient device 104 to check-in for a flight and print a boarding passand/or a receipt. To that end, the client device 104 can include one ormore other devices physically integrated therein. Example devices caninclude a scanner (e.g., a barcode scanner, a QR code scanner), a scale(e.g., to weigh luggage), a printer (e.g., to print boarding passesand/or receipts) and a reader (e.g., credit card, driver license and/orpassport reader). As discussed in detail below, the client device 104can communicate with other devices that can be indirectly connected tothe client device 104.

Continuing with the example context, one or more of the server devices108 can execute an integrated reservation and inventory managementsystem (“reservation system”) provided as one or more computer programs.In some examples, the reservation system enables passengers to booktravel on a travel conveyance and, at the time of travel, check-in. Insome examples, the reservation system enables agents of travel providersto check-in and board passengers to the travel conveyance. To that end,the client devices 102, 104 can communicate with the one or more serverdevices 108 to facilitate travel reservation, check-in and/or boardingusing the reservation system.

A check-in workflow for travel passengers in the airline industry, forexample, can include several different check-in steps, during which thereservation system is accessed. For example, a check-in workflow caninclude one or more steps related to searching for passengerinformation, assigning seats, handling baggage, adding optionalservices, receiving payments, and/or finalizing the passenger check-in.As an example of a passenger search step, a check-in agent can enterpassenger identification information to locate a particular passenger'stravel itinerary within the reservation system to begin the check-inprocess. For example, a reader (e.g., reader) can be used to read creditcard, driver's license and/or passport information to confirm passengeridentity. In a seat assignment step, the check-in agent can assign aseat to a passenger or can modify an existing seat assignment to ensurethat the passenger is seated in a particular desired seat location orsection. In a baggage handling step, the passenger can be allowed tocheck one or more bags at the check-in counter. The baggage can beweighed (e.g., using the scale 124) to ensure that the baggage adheresto weight limits. In a payment step, the passenger can provide paymentfor the segment or additional services, including for example, checkingan oversized bag or upgrading a seat to first class. In some examples,payment can be provided using a credit card which can be read using areader (e.g., the reader 128). After all of the other check-inprocedures have been completed, a finalization step may be provided tocomplete the check-in process. In some examples, one or more boardingpasses and/or receipts can be printed (e.g., using the printer 126).

A boarding workflow for travel passengers in the airline industry, forexample, can include several different boarding steps, during which thereservation system is accessed. For example, a boarding pass can bescanned (e.g., using the scanner 122) to board the passenger.Information provided on the boarding pass can be compared withinformation provided in the reservation system. If there is nodiscrepancy, boarding of the passenger can be confirmed and recorded atthe reservation system. In some examples, boarding can be visuallyand/or audibly confirmed using a light (e.g., a green light) and/or atone indicating that the passenger has been boarded. If there is adiscrepancy, boarding of the particular passenger can be inhibited. Insome examples, inhibiting passenger boarding can be visually and/oraudibly indicated using a light (e.g., a red light) and/or a toneindicating that the passenger has not been boarded. An issue preventingthe passenger boarding can be resolved and the passenger can be boarded.For example, the seat information on the boarding pass might notcorrespond to the seat information provided in the reservation system.For example, the passenger's seat assignment might have been changedafter check-in, but prior to boarding. In such an example, a newboarding pass reflecting the correct seat assignment can be printed, andthe passenger can be boarded using the new boarding pass.

Implementations of the present disclosure are directed to an externaldevice service (EDS) that enables communication between one or moredevices (e.g., a scanning device, a scale, a printer, a reader) and areservation system. In some examples, the EDS enables data generatedusing a device to be provided in an appropriate format for handling andprocessing by the reservation system and/or client devices (e.g., theclient devices 102, 104). In some examples, the EDS enables datagenerated using the reservation system and/or client devices (e.g., theclient devices 102, 104) to be provided in an appropriate format forhandling and processing by a device (e.g., a scanning device, a scale, aprinter, a reader). In some implementations, the EDS can include a localEDS and/or a server EDS. The local EDS can be provided on one or moreclient devices (e.g., the client devices 102, 104) and the server EDScan be provided on one or more server devices (e.g., the server devices108). The EDS can be provided as one or more computer programs that canbe executed using one or more processors.

FIG. 2 is a detailed block diagram of components of the system 100 ofFIG. 1. In FIG. 2, the system 100 includes the client device 102, aserver device 108 and the network 110. As discussed in further detailherein, the client device 102 can be in communication with the scanner122, the scale 124, the printer 126 and/or the reader 128. Although theclient device 104 of FIG. 1 is not depicted in FIG. 2, it is appreciatedthat implementations of the present disclosure are readily operable withthe client device 104 and any other appropriate client device. Further,and although a single server device 108 is depicted in FIG. 2, it isappreciated that implementations of the present disclosure are readilyoperable with one or more server devices 108. In FIG. 2, the system 100further includes a printer 200 and a printer 202. In some examples, theprinter 200 can include a networked printer. In some examples, theprinter 202 can include a Transmission Control Protocol/InternetProtocol (TCP/IP) printer. In some examples, a networked printerincludes a printer that uses print drivers setup in an operating system.In some examples, a TCP/IP printer includes a printer that directlyreceives raw data over a TCP/IP communication port.

The server device 108 executes a server EDS 210 and the client device102 executes a local EDS 212. In some examples, the local EDS 212 can beprovided as part of a user interface (UI) executed on the client device102. As discussed in further detail herein, the server EDS 210 enablesdata to be communicated to and/or from devices (e.g., the printers 200,202), and/or to and/or from the local EDS 212. Similarly, the local EDS212 enables data to be communicated to and/or from devices (e.g., thescanner 122, the scale 124, the printer 126, the reader 128, theprinters 200, 202), and/or to and/or from the server EDS 210.

In some examples, the local EDS 212 enables data to be communicated toand/or from a third party system 220 that can be in furthercommunication with a third party device. In the depicted example, athird party device 222 is provided as a third party printer, but is notlimited to third party printers. In some examples, the third partydevice can include a common use terminal equipment (CUTE) system or acommon use self-service (CUSS) system. An example CUTE system caninclude an agent terminal that is travel service provider agnostic andthat can be used by various travel service providers over a given timeperiod. For example, the agent terminal can be used by a first travelservice provider for checking in and/or boarding passengers for a travelconveyance that is operated by the first travel service provider. Theagent terminal can be subsequently used by a second travel serviceprovider for checking in and/or boarding passengers for another travelconveyance that is operated by the second travel service provider. Inthis manner, a single gate, at an airport for example, can be used bydifferent airlines (i.e., travel service providers). An example CUSSsystem can include a check-in kiosk that is travel service provideragnostic and that can be used by passengers to check in for a travelconveyance regardless of the particular travel service provider thatthey are traveling with.

The server EDS 210 includes one or more formatter services 230, a dataservice 232 and one or more server communication services 234. In someexamples, each formatter service 230 can be provided as a dynamic-linklibrary (DLL) and can be associated with a particular type of externaldevice and/or a particular type of request. For example, a formatterservice 230 can be associated with a particular type of printer andprint request. Within the example context of airline travel, exampleprint requests can include a print boarding pass request, a printbaggage tag request, a print receipt request and a print itineraryrequest, and example types of printers can include a networked printer,a TCP/IP printer, a local printer (i.e., connected to a client device),or a third party printer. The formatter service 230 generates aparticular data stream based on the type of external device and therequest. For example, the formatter service 230 converts the requestfrom a format that the request was originally provided in (a firstformat) to a format that the external device can process (a secondformat). The formatter service 230 also processes communication resultsreceived back from an external device. In some examples, the formatterservice 230 translates the communication results from a format of theexternal device (the second format) to a format for further processingby the UI (the first format), as discussed in further detail below.

In some examples, the data service 232 can be provided as one or morecomputer program modules or sub-modules. The data service 232 canprovide information that defines how a data stream should be formattedfor a particular type of external device and/or a particular type ofrequest. In some examples, the data service 232 provides formattinginformation to a formatter service 230 that is handling a particularrequest (i.e., that is formatting the data stream). In some examples,the data service 232 retrieves the formatting information from adatabase. In some examples, the data service 232 retrieves theformatting information from a default file stored on the server.

In some examples, each server communication service 234 can be providedas a DLL. The server communication service 234 determines how theformatted request is to be communicated to the external device. In someexample, the external device can include a networked device (e.g., theprinters 200, 202). In some examples, the external device can include alocal device that is connected to a client device (e.g., the clientdevice 102, 104). Consequently, the server communication service 234determines whether the request is to be transmitted directly to theexternal device over the network or indirectly to the external deviceover the network and through the client device (e.g., using a duplexcontract connection).

The local EDS 212 includes one or more retrieve local device services240, one or more local device services 242 and one or more communicationservices 244. In some examples, each retrieve local device service 240can be provided as a DLL that is associated with a particular externaldevice. The retrieve local device services 240 determine which localdevice services 242 are to be used with the local EDS 212. In someexamples, the retrieve local device services 240 determine which devicesare connected to the client device and retrieve a local device service242 associated with each device. In some examples, the devices caninclude devices that are set-up with the operating system of the clientdevice. In some examples, retrieve local device services can determinethat the client device is a third party common use workstation andretrieve a list of available devices. In some examples, retrieve localdevice services can retrieve data from a database regarding availableTCP/IP devices (e.g., printers) that can be accessed on the client'snetwork but not the server's network.

In some examples, the retrieve local device services 240 retrieve localdevice services 242 upon start-up of the application that executes theUI. In some examples, each local device service 242 can be provided asone or more computer program modules or sub-modules and handles requeststo and response from devices. In some examples, one or more local deviceservices 242 can communicate with an associated device through acommunication service (e.g., via a driver). In some examples, one ormore local device services can communicate with a device through a thirdparty system (e.g., a device connected to a CUTE system and/or CUSSsystem). In some examples, one or more local device services 242 candirectly interact with the client device 102 (e.g., to perform a “Printto File” operation).

In some examples, each communication service 244 can be provided as aDLL and coordinates communication between a local device service 242 andan associated device. For example, the device can include a printer, andthe communication service 244 can determine whether communication withthe printer is achieved directly or through a driver (e.g., convertingthe request to bytes to be processed by a driver), and can facilitatesuch communication. Communication services 244 can facilitatecommunication with devices such as printers, boarding gate readers(e.g., including machine-readable scanners), scales, readers, scannersand the like.

In some implementations, when the client device 102 is activated the UIcan be executed. The UI enables operator interaction with the clientdevice 102 for passenger check-in and/or boarding, for example. In someexamples, the local EDS 212 is executed as part of the UI. The local EDS212 retrieves relevant RLDSs 240 and LDSs 242. In some examples, a UIconfiguration defines which RLDSs 240 and LDSs 242 that are to beretrieved. In some examples, the local EDS 212 retrieves LDSs 242 fromany retrieved RLDSs 240. For example, an RLDS 240 can communicate with athird party application to generate a list of LDSs 242 to be used withthe third party application. In some examples, the UI configuration caninclude a combination of RLDS and LDS entries that are defined. When theUI starts up, all RLDS and/or LDS entries are retrieved and a list ofLDSs is generated. This list of LDSs can include the LDS entries from aswell as LDSs that are retrieved by one or more RLDS.

Event handlers are setup on all active LDSs 242. In some examples, anactive LDS is a service that handles devices that can actively send datato an application without any action from the application. Examples ofthis include a barcode scanner (e.g., the scanner 122) and a reader(e.g., the reader 128). For example, a passenger boarding applicationcan be executed on the client device 102 and the barcode scanner canscan a barcode of a boarding pass to generate corresponding data that isprocessed through the boarding application. A passive LDS is a servicethat wraps devices that will not send data except in response to anapplication action. An example is a printer (e.g., the printer 126)),where the application sends the print stream to the printer before theprinter response is returned.

The UI registers with the local EDS 212 for all events from the activeLDS. In some examples, the UI subscribes to active LDS events, such thata published LDS event is provided to the UI in a publish/subscribeparadigm.

In accordance with implementations of the present disclosure, one ormore external devices can be connected and can be communicated withwithout disrupting the base system. In general, when an external deviceis added (e.g., a networked device and/or a local device), the UIconfiguration is updated and one or more DLLs are added. In someexamples, the UI configuration is updated to identify a particular DLLthat is to be used based on device type and request. In some examples,the one or more DLLs can include a formatter service 230 and/or a servercommunication service 234 at the server EDS 210, and/or a retrieve localdevice service 240 at the local EDS 212. In this manner, new externaldevices can be quickly integrated into the overall system with minimaleffort (e.g., no direct coding is required in the application executingon the client device).

In some examples, an active device can send data to the applicationexecuting on the client device without prompting by the application. Forexample, the scanner 122 can scan a machine-readable code (e.g., abarcode or a QR code) to generate scanned data. The scanned data iscommunicated to a corresponding LDS 242 (i.e., the LDS that handles theparticular device) through a corresponding communication service 244(i.e., the communication service that enables communication with theparticular device). The LDS that handles the particular device receivesthe scanned data and generates an LDS event that includes the scanneddata. In some examples, the LDS event includes a device identifier, thetype of data (e.g., barcode data, credit card data) and the scanneddata. By using an LDS event, the LDS is able to hand off the handling ofthe event to the application executed on the client device and canreturn to a “waiting for data” state. In this manner, the LDS does notmiss a scan while the last scanned data is processed.

The local EDS 212 handles the LDS event and generates an EDS event thatincludes the scanned data. In some examples, the EDS event can includethe device identifier, the type of data (e.g., barcode data, credit carddata) and the scanned data. By using the EDS event, the EDS is able tohand off the handling of the event to the application executed on theclient device and return to a “waiting for data” state (i.e., waitingfor data from an active LDS). In this manner, the EDS does not miss LDSevent while the most recently received data is processed. Accordingly,two layers of events (LDS events and EDS events) can be provided. Inthis manner, the EDS can function as a single point of communication tothe external device service. That is, it is up to the EDS to gather andhandle events from all of the different LDSs. The UI and the applicationhandle the EDS event and perform some action based thereon. For example,a passenger can be boarded in response to the EDS event.

In some examples, the client device 102 can request that a non-localdevice be used to execute some function. For example, the client device102 can request that a document (e.g., a boarding pass) be printed usingone of the printers 200, 202. In some examples, the UI can generate anexternal device request and can send the external device request to theserver device 108 over the network 110. In some examples, the requestfrom the client device 102 to the server device 108 can includeinformation to identify the type of document to be printed, and whichpassenger and flight(s) should be included on the boarding pass. Theserver device 108 can process the external device request to identifywhich device should be used to fulfill the external device request andbuilds a server EDS request. In some examples, the EDS request includesa large amount of data associated with the booking, passengers and/orflights. In this manner, the data is available to be printed ondocuments (e.g., receipts, boarding passes) and can be tailored for thepurposes of a particular travel service provider.

The server EDS request is processed using the server EDS 210. In someexamples, the server EDS 210 retrieves formatter routing data from thedata service 232 and uses the formatter routing data to determine whichformatter service 230 to use based on the given request type and theexternal device. The server EDS uses the identified formatter service230 to build a communication request. In some examples, thecommunication request can include a list of data streams that will besent to the device. In some examples, the formatter service 230 is alsoable to call a third party to retrieve appropriate data streams. In someexamples, the formatter service 230 takes the given request and externaldevice to build the communication request. In some examples, theformatter service 230 can call the data service 232 to retrieveformatting data. In some examples, the formatter service 230 can useintelligent formatting technology to format the data.

The server EDS 210 retrieves server communication routing data from thedata service 232. The server EDS 210 uses the server communicationrouting data to identify a server communication service 234 based on thegiven external device. The server EDS 210 uses the identified servercommunication service 234 to communicate with the external device. Theserver communication service can transmit the server EDS request to theexternal device.

In some implementations, the server EDS request can be transferred byTCP/IP (e.g., to the printer 202) or network 110 for directcommunication with the external device (i.e., direct communication fromthe server device 108 to the external device). The server EDS request istransmitted directly to the external device, and the external device canreturn a result of the communication.

In some implementations, the server EDS request can be indirectlycommunicated to the external device. For example, the server EDS 210 cancommunicate with the local EDS 212 using a contract (e.g., a duplexcontract) back to the UI for local communication with the externaldevice. In some examples, the local EDS 212 receives the server EDSrequest and identifies a LDS 242 based thereon. The LDS 242 communicatesthe server EDS request to the external device. In some examples, the LDS242 retrieves the local communication routing data from the data service232 of the server EDS 210 to determine which communication service 244to use. In some examples, the LDS 242 can communicate with the dataservice 232 through a WCF connection over the network 110. The selectedcommunication service 244 transmits the server EDS request directly tothe external device and the result of the communication with the deviceis returned. In some examples, an LDS 242 can communicate with devicesthrough a third party system (e.g., the printer 222 of the third partysystem 220). The result of the communication with the third party systemis returned. The result of the communication with the external device isreturned from the LDS 242 to the server EDS 210, from which the serverEDS request had originated. The local EDS 212 returns the communicationresult of using the external device to the server communication service234.

In some implementations, the result of the communication with theexternal device (whether direct or through the local EDS 212) isreturned from the server communication service 234 to the formatterservice 230. The formatter service 230 translates the communicationresult into a server EDS response. For example, a device and/or thirdparty systems can return an error code (e.g., printer out of papererror). The formatter service 230 is able to translate received errorcodes and into a message that can be processed by the applicationexecuting on the client device (e.g., to display a “Printer Out ofPaper” message). The server device 108 transmits the server EDS responseto the client device 102. The client device 102 processes the server EDSresponse and the UI displays the result of using the external device tothe user.

FIG. 3 depicts a flowchart of an example process 300 that can beexecuted in implementations of the present disclosure. The exampleprocess 300 can be provided using one or more computer programs that canbe executed using one or more computing devices (e.g., the client device102 and/or the client device 104). The example process 300 can beexecuted to enable a user interface executing on a computing device toreceive data from one or more active devices communicating with thecomputing device.

A local EDS is executed (302). For example, the local EDS 212 can beexecuted as part of a UI executing on the client device 102. One or moreLDSs defined in the UI configuration are retrieved (303). One or morerelevant RLDSs are processed based on the UI configuration to retrieveindicated LDSs (304). For example, the local EDS 212 processes the RLDSs240 to determine which LDSs 242 are to be retrieved. Event handlers aresetup on all active LDSs (306). The UI registers with the local EDS forall events from the active LDSs (308).

FIG. 4 depicts a flowchart of an example process 400 that can beexecuted in implementations of the present disclosure. The exampleprocess 400 can be provided using one or more computer programs that canbe executed using one or more computing devices (e.g., the client device102 and/or the client device 104). The example process 400 can beexecuted to execute one or more operations based on and in response todata generated by a device.

Device data is received at an LDS (402). For example, an active devicecan send data to a corresponding LDS 242 (i.e., the LDS that handles theparticular device) through a corresponding communication service 244(i.e., the communication service that enables communication with theparticular device). A first event is generated based on the device data(404). For example, the LDS 242 generates the first event, whichincludes the device data. The first event is published (406). A secondevent is generated based on the first event (408). For example, thelocal EDS 212 processes the first event and generates a second eventthat includes the scanned data. The second event is published (410). Oneor more operations are executed based on the second event (412). Forexample, the UI processes the second event and performs some actionbased thereon.

FIG. 5 depicts a flowchart of an example process 500 that can beexecuted in implementations of the present disclosure. The exampleprocess 500 can be provided using one or more computer programs that canbe executed using one or more computing devices (e.g., the client device102, the client device 104 and/or the server devices 108). The exampleprocess 500 can be executed to enable communication with externaldevices.

An external device request is generated (502). The external devicerequest is transmitted (504). For example, the UI executing on a clientdevice 102, 104 can generate an external device request and can send theexternal device request to the server device 108 over the network 110.The external device request is received and an external device isidentified (506). For example, the server device 108 receives andprocesses the external device request to identify which external deviceshould be used to fulfill the external device request. A server requestis generated (508). For example, the server device 108 generates aserver EDS request based on the identified external device. Formatterrouting data is retrieved (510). For example, the server request isprocessed using the server EDS 210, which retrieves formatter routingdata from the data service 232. A formatter service is selected (512).For example, the server EDS 210 uses the formatter routing data todetermine which formatter service 230 to use based on the given requesttype and the external device. A communication request is built (514).For example, the server EDS 210 uses the identified formatter service230 to build the communication request. Server communication routingdata is retrieved (516). For example, the server EDS 210 retrievesserver communication routing data from the data service 232.

A server communication service is selected (518). For example, theserver EDS 210 uses the server communication routing data to identify aserver communication service 234 based on the given external device. Theserver request is transmitted to the external device (520). For example,the server EDS 210 uses the selected server communication service 234 totransmit the server EDS request to the external device. A communicationresult is received (522). For example, the result of the communicationwith the external device (whether direct or through the local EDS 212)is received by the server communication service 234 and is provided tothe formatter service 230. The communication result is translated toprovide a server response (524). For example, the formatter service 230translates the communication result into a server EDS response, and theserver device 108 transmits the server EDS response to the client device102, 104. The server response is received (526). The server response isprocessed to perform one or more operations. For example, the externaldevice result is displayed using the UI (528). For example, the clientdevice 102, 104 processes the server EDS response and the UI displaysthe result of using the external device to the user.

Implementations of the present disclosure provide one or more of thefollowing attributes. In some aspects, formatter routing, servercommunication routing and local communication routing enable newformatter services and communication services corresponding to newlyconnected devices to be plugged in without making a change to theoverall external device architecture. In some aspects, the externaldevice architecture is able to handle devices that actively send data toapplications executing on the client device as well as passive devicesthat are used by the applications. In some aspects, the external devicearchitecture is able to handle communication with devices on the networkas well as local devices connected to the client device (e.g., a user'sworkstation). In some aspects, the use of a generic communicationinterface enables the external device architecture to support manydifferent types of request and response objects.

Implementations of the present disclosure and all of the functionaloperations provided herein can be realized in digital electroniccircuitry, or in computer software, firmware, or hardware, including thestructures disclosed in this specification and their structuralequivalents, or in combinations of one or more of them. Implementationsof the invention can be realized as one or more computer programproducts, i.e., one or more modules of computer program instructionsencoded on a computer readable medium for execution by, or to controlthe operation of, data processing apparatus. The computer readablemedium can be a machine-readable storage device, a machine-readablestorage substrate, a memory device, or a combination of one or more ofthem. The term “data processing apparatus” encompasses all apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, or multiple processors or computers.The apparatus can include, in addition to hardware, code that creates anexecution environment for the computer program in question, e.g., codethat constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, or a combination of one or moreof them.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, and it can bedeployed in any form, including as a stand alone program or as a module,component, subroutine, or other unit suitable for use in a computingenvironment. A computer program does not necessarily correspond to afile in a file system. A program can be stored in a portion of a filethat holds other programs or data (e.g., one or more scripts stored in amarkup language document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub programs, or portions of code). A computer programcan be deployed to be executed on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described in this disclose can beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both. The essential elements of a computer area processor for performing instructions and one or more memory devicesfor storing instructions and data. Generally, a computer will alsoinclude, or be operatively coupled to receive data from or transfer datato, or both, one or more mass storage devices for storing data, e.g.,magnetic, magneto optical disks, or optical disks. However, a computerneed not have such devices. Moreover, a computer can be embedded inanother device, e.g., a mobile telephone, a personal digital assistant(PDA), a mobile audio player, a Global Positioning System (GPS)receiver, to name just a few. Computer readable media suitable forstoring computer program instructions and data include all forms ofnon-volatile memory, media and memory devices, including by way ofexample semiconductor memory devices, e.g., EPROM, EEPROM, and flashmemory devices; magnetic disks, e.g., internal hard disks or removabledisks; magneto optical disks; and CD ROM and DVD-ROM disks. Theprocessor and the memory can be supplemented by, or incorporated in,special purpose logic circuitry.

To provide for interaction with a user, implementations of the inventioncan be implemented on a computer having a display device, e.g., a CRT(cathode ray tube) or LCD (liquid crystal display) monitor, fordisplaying information to the user and a keyboard and a pointing device,e.g., a mouse or a trackball, by which the user can provide input to thecomputer. Other kinds of devices can be used to provide for interactionwith a user as well; for example, feedback provided to the user can beany form of sensory feedback, e.g., visual feedback, auditory feedback,or tactile feedback; and input from the user can be received in anyform, including acoustic, speech, or tactile input.

Implementations of the present disclosure can be realized in a computingsystem that includes a back end component, e.g., as a data server, orthat includes a middleware component, e.g., an application server, orthat includes a front end component, e.g., a client computer having agraphical user interface or a Web browser through which a user caninteract with an implementation of the present disclosure, or anycombination of one or more such back end, middleware, or front endcomponents. The components of the system can be interconnected by anyform or medium of digital data communication, e.g., a communicationnetwork. Examples of communication networks include a local area network(“LAN”) and a wide area network (“WAN”), e.g., the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

While this disclosure contains many specifics, these should not beconstrued as limitations on the scope of the disclosure or of what maybe claimed, but rather as descriptions of features specific toparticular implementations of the disclosure. Certain features that aredescribed in this disclosure in the context of separate implementationscan also be provided in combination in a single implementation.Conversely, various features that are described in the context of asingle implementation can also be provided in multiple implementationsseparately or in any suitable sub-combination. Moreover, althoughfeatures may be described above as acting in certain combinations andeven initially claimed as such, one or more features from a claimedcombination can in some cases be excised from the combination, and theclaimed combination may be directed to a sub-combination or variation ofa sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the implementations described above should not beunderstood as requiring such separation in all implementations, and itshould be understood that the described program components and systemscan generally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular implementations of the present disclosure have beendescribed. Other implementations are within the scope of the followingclaims. For example, the actions recited in the claims can be performedin a different order and still achieve desirable results.

What is claimed is:
 1. A computer-implemented method for facilitatingtravel on a travel conveyance, the method executed using one or moreprocessors and comprising: executing a user interface on a computingdevice, the computing device being used by a user to facilitate thetravel on the travel conveyance; determining that a first device isconnected for local communication with the computing device, and inresponse, updating a configuration of the user interface to integratethe first device; generating first and second event handlers executed onthe computing device, each of the first and second event handlerscorresponding to a respective local device service file; receiving firstdata at the first event handler of the one or more event handlers, thefirst event handler corresponding to a first local device serviceassociated with the first device; generating, using the first eventhandler, a first event that comprises the first data; receiving, at alocal external device service, the first event; generating, using thelocal external device service, a first external device event based onthe first event; performing a first action based on the first externaldevice event, the first action being associated with fulfilling thetravel on the travel conveyance; receiving second data at the secondevent handler of a second local device service associated with a seconddevice that is in electronic communication with the computing device;generating, using the second event handler, a second event thatcomprises the second data; receiving, at the local external deviceservice, the second event; generating, using the local external deviceservice, a second external device event based on the second event; andperforming a second action based on the second external device event. 2.The computer-implemented method of claim 1, further comprising:receiving the second local device service; and storing the second localdevice service.
 3. The computer-implemented method of claim 1, whereinthe first event handler subscribes to events generated by at least thefirst device.
 4. The computer-implemented method of claim 1, wherein acommunication service enables communication of the first data from thefirst device to the first local device service, and the communicationservice is exclusive to the first device and to the first local deviceservice.
 5. The computer-implemented method of claim 1, wherein thefirst event further comprises a device identifier of the first deviceand a type of the first data.
 6. The computer-implemented method ofclaim 1, wherein the first external device event comprises a deviceidentifier of the first device, a type of the first data, and the firstdata.
 7. The computer-implemented method of claim 1, wherein each localdevice service file is provided as a dynamic link library (DLL) file. 8.The computer-implemented method of claim 1, wherein the first device isa scanner or a scale.
 9. The computer-implemented method of claim 1,wherein the computing device is a kiosk or a terminal.
 10. Thecomputer-implemented method of claim 1, wherein the first actioncomprises checking in a passenger for travel on a travel conveyance orboarding a passenger for travel on a travel conveyance.
 11. Anon-transitory computer-readable storage medium coupled to one or moreprocessors and having instructions stored thereon which, when executedby the one or more processors, cause the one or more processors toperform operations for facilitating travel on a travel conveyance, theoperations comprising: executing a user interface on a computing device,the computing device being used by a user to facilitate the travel onthe travel conveyance; determining that a first device is connected forlocal communication with the computing device, and in response, updatinga configuration of the user interface to integrate the first device;generating first and second event handlers executed on the computingdevice, each of the first and second event handlers corresponding to arespective local device service file; receiving first data at the firstevent handler of the one or more event handlers, the first event handlercorresponding to a first local device service associated with the firstdevice; generating, using the first event handler, a first event thatcomprises the first data; receiving, at a local external device service,the first event; generating, using the local external device service, afirst external device event based on the first event; performing a firstaction based on the first external device event, the first action beingassociated with fulfilling the travel on the travel conveyance;receiving second data at the second event handler of a second localdevice service associated with a second device that is in electroniccommunication with the computing device; generating, using the secondevent handler, a second event that comprises the second data; receiving,at the local external device service, the second event; generating,using the local external device service, a second external device eventbased on the second event; and performing a second action based on thesecond external device event.
 12. A system comprising: one or moreprocessors; and a computer-readable storage medium coupled to the one ormore processors having instructions stored thereon which, when executedby the one or more processors, cause the one or more processors toperform operations for facilitating travel on a travel conveyance, theoperations comprising: executing a user interface on a computing device,the computing device being used by a user to facilitate the travel onthe travel conveyance; determining that a first device is connected forlocal communication with the computing device, and in response, updatinga configuration of the user interface to integrate the first device;generating first and second event handlers executed on the computingdevice, each of the first and second event handlers corresponding to arespective local device service file; receiving first data at the firstevent handler of the one or more event handlers, the first event handlercorresponding to a first local device service associated with the firstdevice; generating, using the first event handler, a first event thatcomprises the first data; receiving, at a local external device service,the first event; generating, using the local external device service, afirst external device event based on the first event; performing a firstaction based on the first external device event, the first action beingassociated with fulfilling the travel on the travel conveyance;receiving second data at a second event handler of a second local deviceservice associated with a second device that is in electroniccommunication with the computing device; generating, using the secondevent handler, a second event that comprises the second data; receiving,at the local external device service, the second event; generating,using the local external device service, a second external device eventbased on the second event; and performing a second action based on thesecond external device event.
 13. The system of claim 12, wherein thefirst event handler subscribes to events generated by at least the firstdevice.
 14. The system of claim 12, further comprising: a communicationservice configured to enable communication of the first data from thefirst device to the first local device service, and the communicationservice is exclusive to the first device and to the first local deviceservice.
 15. The system of claim 12, wherein the first event furthercomprises a device identifier of the first device and a type of thefirst data.
 16. The system of claim 12, wherein the first externaldevice event comprises a device identifier of the first device, a typeof the first data, and the first data.
 17. The system of claim 12,wherein each local device service file is provided as a dynamic linklibrary (DLL) file.
 18. The system of claim 12, wherein the first deviceis a scanner or a scale.
 19. The system of claim 12, wherein thecomputing device is a kiosk or a terminal.
 20. The system of claim 12,wherein the first action comprises checking in a passenger for travel ona travel conveyance or boarding a passenger for travel on a travelconveyance.